Search results for "software process"

Experiences from Software Maintenance Seminars: Organizing Three Seminars with 127 Groups

2009

Software maintenance and evolution (SME) is an important but problematic topic-area for university-level computer science education. Seminars can be used to provide versatile and up-to-date knowledge for students regarding scientifically relevant issues. We have organized three systematic university-level seminars on SME with a total of 127 seminar groups. Each group has been assigned a task of analyzing one scientific SME-article. The main results include the general confirmed feasibility of the selected seminar-based approach. The paper describes the background of the seminars, their contents, and experiences concerning organization and feasibility of the seminars. The results support org…

Software Business in the Telecommunications Sector

2012

Operations and Business Support Systems (OSS/BSS) software of Communication Service Providers (CSP's) can be developed internally within the CSP or acquired from a Software Vendor. The software industry lifecycle model hypothesizes that software development is internal in the beginning of the industry's lifecycle, and that the share of external products increases when it matures. Empirical evidence shows signs of the OSS/BSS software industry approaching maturity. Current and future developments of the industry include the possibilities of utilizing the Software-as-a-Service (SaaS) model and Open Source software (OSSw). Both have gained increasing interest by the CSP's. However, the relativ…

Four fundamental software process modelling principles : the Case of Nokia Telecommunications

1997

Fault-proneness of open source software: Exploring its relations to internal software quality and maintenance process

2013

The goal of this study is to explore how fault-proneness of open source software (OSS) could be explained in terms of internal quality attributes and maintenance process metrics. We reviewed earlier studies and performed a multiple case study of eight Java-based projects based on data available in the Source Forge repository. Overall, we studied 342 re- leases of those systems. As is usual, software quality was regarded as a set of internal and external quality attributes. A to- tal of 76 internal quality attributes were measured from the source code of the selected systems via the tool SoftCalc. Two external quality attributes contributing to fault-proneness were in turn obtained from the …

Apathy Towards the Integration of Usability Work: A Case of System Justification

2016

In this article we report from a case study of a software development organization and we study in particular the developers’ and product managers’ attitudes towards integrating usability work into software development. We offer explanations based on system justification theory illuminating what would-be integrators might be up against. The analysis shows how the developers only pay lip service to usability work and how they treat users superficially. It further shows how that leads to stereotyping of usability designers and users in order to preserve status quo, and how internalization of inequality between the developers and usability designers rationalizes the preservation of status quo.…

Using organizational influence processes to overcome IS implementation barriers: lessons from a longitudinal case study of SPI implementation

2014

A fundamental tenet of the information systems (IS) discipline holds that: (a) a lack of formal power and influence over the organization targeted for change, (b) weak support from top management, and (c) organizational memories of prior failures are barriers to implementation success. Our research, informed by organization influence, compellingly illustrates that such conditions do not necessarily doom a project to failure. In this paper, we present an analysis of how an IS implementation team designed and enacted a coordinated strategy of organizational influence to achieve implementation success despite these barriers. Our empirical analysis also found that technology implementation and …

A modest but practical software process modeling technique for software process improvement

2002

One of the main problems with software engineering is due to the difficulties in evaluating and improving our software processes, especially in the light of the fact that reuse depends on a process which supports it. Generally used approaches to the evaluation and improvement of software processes are based on the CMM, for example. In this paper we present a technique to improve software processes through modeling and evaluation. The presented technique is fairly easy to use, provides reasonably good results and requires only a fraction of resources required by CMM appraisals. Copyright © 2002 John Wiley & Sons, Ltd.

Requirements Engineering and Process Modelling in Software Quality Management— Towards a Generic Process Metamodel

2004

This paper examines the concept of Quality in Software Engineering, its different contexts and its different meanings to various people. It begins with a commentary on quality issues for systems development and various stakeholders' involvement. It revisits aspects and concepts of systems development methods and highlights the relevance of quality issues to the choice of a process model. A summarised review of some families of methods is presented, where their application domain, lifecycle coverage, strengths and weaknesses are considered. Under the new development era the requirements of software development change; the role of methods and stakeholders change, too. The paper refers to the …

Use and Identification of Components in Component-Based Software Development Methods

2000

New software systems are needed ever more but to keep up with this trend software developers must learn to create quality software more efficiently. One approach is to (re-)use components as building blocks of the new software. Recently there has been more interest to create component-based software development methods to support this. In this article we first set out requirements for reuse-based software development and then evaluate three component-based methods, namely Catalysis, OMT++, and Unified Process. As a conclusion we argue that evaluated methods produce prefabricated components and that component-based means that software developers can change better components to existing syste…

Vertical Software Industry Evolution: The Impact of Software Costs and Limited Customer Base

2013

ContextSoftware systems are commonly used in a variety of industries as a means of automating organizational business processes. Initially, such software is often developed in-house by the vertical organizations possibly with the support of professional IT service providers; however, in many cases, internally developed software is eventually replaced with the software products provided by independent software vendors. These vendors often use license fees to recover their software development investments, as well as to gain some margin. However, if the vendor's customer base for a specific type of software is limited, then either the license fees are too high and hence the customers may pref…